Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

• Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
• Select "Create new custom chat mode file"

• 下のような指定を:rootに指定しておく。

:where(:root) {
  overflow-wrap: anywhere; /* 収まらない場合に折り返す */
  /* word-break: initial; 単語の分割はデフォルトに依存（初期値のため指定しなくて良い） */

• System Awareness: Before implementation, map the dependency graph and system topology. Ensure local changes preserve global invariants and do not trigger "Shotgun Surgery."
• Orthogonality: Design for independence. Ensure that changes in one module do not leak side effects into others. Minimize coupling and maximize cohesion.

• Intent-Revealing Design: Prioritize human readability and intent over machine cleverness. Use naming that explains "Why" rather than "How."
• Single Level of Abstraction (SLA): Adhere strictly to the Single Responsibility Principle (SRP). Each function must operate at a consistent level of abstraction and have exactly one reason to change.

Verification-Driven Development (VDD) is a high-integrity software engineering framework designed to eliminate "code slop" and logic gaps through a generative adversarial loop. Unlike traditional development cycles that rely on passive code reviews, VDD utilizes a specialized multi-model orchestration where a Builder AI and an Adversarial AI are placed in a high-friction feedback loop, mediated by a human developer and a granular tracking system.

How to use this script:

1. Accept a quest under Discover -> Quests
2. Press Ctrl+Shift+I to open DevTools
3. Go to the Console tab
4. Paste the following code and hit enter:

This document captures current best practices for R development, emphasizing modern tidyverse patterns, performance, and style. Last updated: August 2025

1. Use modern tidyverse patterns - Prioritize dplyr 1.1+ features, native pipe, and current APIs
2. Profile before optimizing - Use profvis and bench to identify real bottlenecks
3. Write readable code first - Optimize only when necessary and after profiling
4. Follow tidyverse style guide - Consistent naming, spacing, and structure

Run two Claude Code accounts simultaneously on macOS without re-authenticating by using separate configuration directories.

1. Create Separate Config Directories

   mkdir ~/.claude-account1
   mkdir ~/.claude-account2